5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.IMPORT CGI DATA


This subroutine populates Appx variables from STDIN.

Usage:

Description:

This subroutine populates Appx variables from STDIN. No parameters are required.

This can only be used in Appx sesssions that have been invoked by a web server. Running this in a normal Appx session will cause the session to hang or crash.

APPX understands how to parse CGI data into APPX variables. It picks apart the CGI data string and looks for variable NAMEs that match an APPX variable name and sets the variable accordingly. This acts as a SET statement where the sender is always alpha. So, if you use the ALPHA representation of a DATE field, then when APPX fills the date field from the CGI data, it will do the correct conversion from the ALPHA value.

The format of your CGI NAMEs for variables must match the pattern that APPX understands: AAA:BBBB BBB(CCC)=DDDDDD, where AAA is the Application ID (optional), BBBB BBB(CCC) is the APPX variable (with optional occurrence), and DDDDDD is the value. Optional occurrences should use leading zeroes for a total of 3 characters. If the Application Id is missing, Appx will default to the current application.

The environment variable CONTENT_LENGTH must be set to the size of the text being imported before invoking APPX, else APPX will fail or hang during startup. This is usually set by the web server itself.

Note that you can use this routine as many times a you like in the session, it is not a destructive parse of the incoming STDIN data. For example, you may have one standard application that receives web requests. It can call this routine to determine what to do next, and invoke another Appx process. That Appx process can also call this routine to populate the variables it is interested in, and so on.

To see the details of the processing this subroutine, set the environment variable APPX_CGIDATA_LOG=<filename>.

See document "Using CGI to Interface with the Web" for more detailed information. You may also want to refer to the document "Introduction to Web Server" for the basics of this concept.

Application Design Manual                                         "Powered by Appx Software"

1193

©2006 By APPX Software, Inc. All Rights Reserved